Development / Production Recommended Workflow?

[Craig Ozancin]

For what it's worth, here is my approach.

I use this with hg-evolve / topics.

I use two related repositories:

application              this is the public repository
application-devel    this is a private (non-publishing) repository

Both are related in that application-devel will have all changesets from
application + all draft changes

application-devel also has a additional paths entry that points to
application named public

When I get ready to publish a changeset all I have to do is: hg push -r id
public.I then rebase topics to the top of public changesets.

I will also often set-up a test environment based on the public application
repository and use export/patch to apply candidate changesets. I can
perform code review and run build verification, performance and unit
testing.
.
Craig

On Thu, Aug 5, 2021 at 8:40 AM Alessandro Dentella <
sandro.dentella at gmail.com> wrote:

> On Thu, Aug 05, 2021 at 02:32:33PM +0100, Simon Harrison 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!
>
> A recomended setup is to have local config variables stored in env
> variables or
> in a file that is not registered in mercurial.
>
> You probably have password or tokens you don't want to share and is much
> safer
> not to store in a repository.
>
> It's not difficult to achieve this, just add the local config file to
> .hgignore
>
> At this point you simply push to server and then from server you pull.
>
>
> sandro
> *:-)
>
> _______________________________________________
> 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/8ea23928/attachment-0002.html>