We need a more robust way of deploying a new client brand job.
Current Setup
Hosted on linux VPS
Git hook to individual repo
Push to master deploys updates
We have the (internetboyz lel) node app setup to create new sites on our vps, but this is quite cumbersome to setup each time, so want to move away from it. Also allocating a login/pw to each site is a pain as I need to SSH in to do it + all passwords are shared across the VPS, not such a good one.
Suggestions
I think heroku might be the easy answer to this to begin with, and suggests we should probably use rails to scaffold v1 out even if we're not doing serious user input stuff yet. This way we can manage all brands under the same repo - use one server instance purely for brandguide.io, and deploy feature updates globally to all the brands (if they're sharing templates, for example).
Also, password management will be handled by rails, rather than the server and presumably we could setup an admin account that can modify client accounts.
Later on, in the case of this thing becoming a real product, we would likely spin up new cloud instances for every client so they are not sharing the same server - but that's a long way away yet.
mattlenz
commented
10 years ago
We need a more robust way of deploying a new client brand job.
Current Setup
We have the (internetboyz lel) node app setup to create new sites on our vps, but this is quite cumbersome to setup each time, so want to move away from it. Also allocating a login/pw to each site is a pain as I need to SSH in to do it + all passwords are shared across the VPS, not such a good one.
Suggestions
I think heroku might be the easy answer to this to begin with, and suggests we should probably use rails to scaffold v1 out even if we're not doing serious user input stuff yet. This way we can manage all brands under the same repo - use one server instance purely for brandguide.io, and deploy feature updates globally to all the brands (if they're sharing templates, for example).
Also, password management will be handled by rails, rather than the server and presumably we could setup an admin account that can modify client accounts.
Later on, in the case of this thing becoming a real product, we would likely spin up new cloud instances for every client so they are not sharing the same server - but that's a long way away yet.