Development / Production Recommended Workflow?

[Stephen Rasku]

Could you use a production branch and a development branch?  You would
merge from develop to production and push to the public server. The
different settings would only live on the production branch.

If the two databases are not compatible you would have to run a migration
script. I don’t have enough details to know if this is necessary, though.

On Thu, Aug 5, 2021 at 6:39 AM Simon Harrison <info at simonh.uk> wrote:

> On Thu, 5 Aug 2021 07:07:46 -0600
> Bob Hood <bhood2 at comcast.net> wrote:
>
> > I think the next step up from the patch approach would be simply to
> > run a web server on your local repo and pull the change to your
> > sever.  This of course assumes you have the ability to (briefly)
> > expose your local repo to the Internet so the server can see it.
> >
> > https://tortoisehg.readthedocs.io/en/latest/serve.html
> >
>
> Thanks Bob. I'm fine with pushing to the server (already push to other
> servers from local for backup purposes). The problem is, I can't quite
> get my head around how to manage the differences between the two
> repo's. Which is why I've not done it yet.
>
> The local one has a different database and some settings are
> different between the two. I'm probably very much under using the
> features of Mercurial!
>
> --
> Web: https://simonh.uk
> Email: mail at simonh.uk
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20210805/11f0b0e0/attachment-0002.html>