You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Feature request #1340: Set up assets subdomain Git repo

Kind feature request
Product wincent.dev
When Created , updated
Status open
Reporter Greg Hurrell
Tags no tags

Description

At the moment I have the wincent.dev code managed in a Git repository but there are some static assets that are not stored in the repo and live only on the server.

They do get backed up with the normal server backup, but I think I'd prefer to track them in a separate repo too.

Given that these assets can arrive there in any number of ways (direct upload, form submission etc) it seems impractical to keep a local copy of the repo and then push to the server copy. (This would involve pushing into a non-bare repo; which is likely to get messy.)

Instead I might make the server copy the "authoritative" one and mirror it out to the usual places.

Will have to think about it.

Comments

  1. Greg Hurrell

    Note that when I posted this I was talking about stuff uploaded into public/system and which survives across deployments.

    Since then I've actually started separating out stuff in a separate assets subdirectory in the wincent.dev Git repo, which is for things which are part of the site but which are specific to certain products (ie. once the site source code is made public those assets will be completely irrelevant to anyone thinking of using the code).

    So just to be clear, the idea that this ticket talks about is not the same thing.

Add a comment

Comments are now closed for this issue.

Menu