Deploy style: Copy files (from SCP to Git)
This is an article in a series on Deployment.
Copying files is essentially the basis of all deployment styles
Deploy with SCP (or rsync over SSH)
Deploying may not be that hard if you’re deploying something static. A simple copy or rsync command may well suffice.
This will work fine for static sites, but more dynamic sites often require more setup. Hence, you will often find some additional scripts that will take care of this. These scripts are imperative in nature.
Variant: deploy with .git
Small applications can be deployed with a true .git deployment: git push and remote pull, directly serving the git repository via a server.
.git based deploy
First time encounter I had with a .git based deployment approach was with Heroku (US based), a service that made deployment easy. You push (git terminology) your app, would configure your database, and it would figure out the ruby version (as declared) and boot it.
Other tools that use this flow are Github and similar Gitlab pages(can be self hosted), solutions (static website) which simulate this behaviour. Netlify made a US based commercial offering around the static site approach.
There is Dokku to have a locally running Heroku clone, and commercially similar services are offered by the EU (France) based Scalingo.
Properties
See for possibilities Deploying Web applications:
- Style: Undecided, perhaps too simple. I’d say imperative, although Doccu/Heroku style might be considered more declarative
- OS virtuality: Out of scope
- Application virtuality: Direct to OS
- From where: Local (but from CI is possible)
- Scope: Application