![]() Possible refactor to push down connection of DeployScanner to appropriate Deployer into deploy package rather than handling in push & preview commands.Clean up some of the interaction between package level variables, command line flags & viper in cmd/root.go.Allow specification of website root in ftp client DONE.Done at a naive level - good enough for me. gitignore) so we don't get random stuff like. sftp is kinda done, but not tested AT ALL, and not plumbed in Modify ftp invocation infrastructure so it is substitutable with another deployment method (e.g.Fix up path handling for directories so they can be relative to working directory rather than absolute.You can disable this using the DontMinify option in the config file or the -m flag. Hugodeploy minifies html, css, js, json and XML by default prior to deploying. This is handy where you have images, videos, bloated javascript libraries etc that are slow to send - they only get sent once. hugodeploy does a binary compare of the file contents ready to deploy with this local copy to determine whether a file needs to be deployed. Hugodeploy keeps a local copy of the latest version of all files successfully sent to to the deployment target. I wanted to use what works out of the box. Rsync should work ok, but some of the lower cost hosting providers don't support it as well as they should. Bash scriptsĪgain, more dynamic dependencies, plus if I have to write code I'd rather write go. your public site gets updated automatically when you commit changes. They do have the advantage that they respond to git commits - i.e. I decided against these as there are just more dynamic dependencies to worry about keeping up to date. This article talks about using Codeship, and this one uses Wercker - both SaaS continous integration and deployment options. What alternatives are there? SaaS Continuous Deployment It is totally independent of any code repository - it just needs the output from whatever static site generator you are using and ftp details for where to put it. ![]() It was originally written to support the deployment of two or three websites I've been working on, starting with A Philosopher and A Businessman. It keeps a local copy of what has already been deployed and figures out what's different each time it is run so it minimises transfers to your web server. This was built to allow easy deployment to el-cheapo hosting providers, such as bluehost and namecheap, with no dependencies on third party deployment systems. created by Hugo) with built-in minification. Simple FTP deployment tool for static websites (e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |