Question

My repository, or at least most of it, is a website. Now Mercurial is great for keeping track of changes and creating the site, but the best way I've come to uploading changes is cloning project-stable to my computer and applying FTP update-all to the host server.

Is it in any way possible to let Kiln push/sync the latest version of project-stable to the server of my site?

During development I sync project-dev on my computer to a sub-directory of the site while editing with Notepad++ and NppFTP at the moment.

Answer 1

Has there been any changes in the FogCreek roadmap concerning this? I am very interested in any kind of solution that would allow me to push changes to my repository, which would then automatically update my dev server.

I see the mention of setting up a webhook and server-side coding. I would be interested in any more information you could provide or any direction you could point me in to set this up. I am not very familiar with webhooks, and I am willing to put the research time in to set this up, but I was hoping on some ideas or clarification on a direction to take the server side coding in.

Any help or direction you could give me with this matter would be greatly appreciated.

Thanks ahead of time for your consideration!

Answer 2

This feature isn't currently available in Kiln and it's unlikely that it will show up on our roadmap. While the feature would certainly be useful for some people, we have to be very cautious of feature-creep in Kiln. Adding FTP functions falls under that umbrella at this stage.

That being said, I'm not here to read the minds of the community, so if anyone thinks this feature would be helpful, please upvote the question (not this answer!) and let us know! We've re-evaluated our positions in the past and there's no reason it can't happen again.

As another option, Mercurial itself does transfer data from place to place pretty well. So a better method might be to install Mercurial on the web server and have it pull changes from Kiln whenever there's a push to the stable repository (you could even alert it to new changes by setting up a webhook and some server-side coding) then just serve the local (to the web server) repository as the site. That would eliminate two data transfers from your process and allow you to essentially keep your website constantly up to date.