staging and dev environments

['Sandro Santilli']

On Thu, Sep 11, 2025 at 11:22:13AM -0400, Regina Obe wrote:
> Sandro Santilli wrote:
> > 
> > I'll rephrase: do we need 2 stages in OSGeo infrastructure ( DNS/Ansible ) ?
> > 
> > DNS:
> > 
> >   *.staging.osgeo.org
> >   *.dev.osgeo.org
> 
> We can have just one is fine with me and we'd use it both for development and staging.

+1, so can we drop *.dev.osgeo.org DNS records as soon as
https://trac.osgeo.org/osgeo/ticket/3419 is completed ?

At the moment we have these:

  *.dev
  dev.geodata (proxied but missing an SSL certificate, says Cloudflare warning)
  dev-nextcloud

> It is only an issue if we have two things going on at the same time.
> E.g. we are trying to make major changes to the theme and also need to test upgrades for current.

We could have many things going on at the same time...
That's where I think the "local" dev environment should be used.
A local dev env could probably also have a local DNS (LXD allows for this I think?)

Having multiple staging at the same time I don't think is a good idea,
as staging serves the purpose of testing if something is ready to become production.

> I can't see a reason why I'd ever want a dev inside an even osgeo4-ansible-dev.

To test deployments, I'd say. Ansible allows you to define *WHERE* to
deploy things, so it's good to test that your changes in the deployment file would work...

> 1) Remember we tried nested nesting nesting and last we tried it didn't work too well

When I first implemented the dev environment it did work for me.
It's failing now because Debian-10 is not available anymore as an
image: https://trac.osgeo.org/osgeo/ticket/3434

> Cause you need 3 levels of nesting for the local computer setup you were proposing.

There is a way to make it work (worked for me), we just need to document it in the README.

> This case we can probably work around by creating ansible-dev as a VM rather than as a container then I think the nesting issue goes away.

Fine with me to use a VM on the OSGeo infra, if really needed
(to be confirmed).

> 2) Wordpress without data is pretty useless for most development and even upgrade testing. 

I disagree on this, I can think of many things that can be tested
without data, in any case the ability to copy data from one running
service to another would be very useful to implement somehow, for
various needs (testing/mirroring/migrations).

--strk; 

  Libre GIS consultant/developer 🎺
  https://strk.kbt.io/services.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/sac/attachments/20250912/7bccb993/attachment.sig>