Ok I will try to dig into where and why we use absolute path and if we do not need I'll implement choice 2 (I am happy you see it same way).
Thank You On Wed, Feb 27, 2019 at 2:42 PM Brian Bouterse <[email protected]> wrote: > I don't know why we're using absolute paths. Option 2 makes sense to me. +1 > > On Wed, Feb 27, 2019 at 8:27 AM David Davis <[email protected]> wrote: > >> By default, django stores relative paths in the database. I'm curious as >> to why we're using absolute paths? >> >> If there's not a reason we need to use absolute paths, then +1 to option >> 2. >> >> David >> >> >> On Wed, Feb 27, 2019 at 1:06 PM Pavel Picka <[email protected]> wrote: >> >>> Hello >>> >>> as working on #4380 I get to state I can change the path from >>> '/var/lib/pulp' to whatever I need but getting hard time to receive old >>> files (when got new location/mount) as artifacts has saved absolute path in >>> the DB. >>> My suggestions are: >>> 1) easy way - user can do change only once before first run/use of pulp >>> 2) my favorite - redo models to save only relative path and add base >>> directory later at runtime from settings >>> 3) hard way - offline db migration (when pulp is not running) to change >>> path of artifacts in DB >>> >>> I would like to ask about your suggestions, opinions and ideas on this >>> how to move this forward. >>> >>> -- >>> Pavel Picka >>> Red Hat >>> _______________________________________________ >>> Pulp-dev mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/pulp-dev >>> >> _______________________________________________ >> Pulp-dev mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/pulp-dev >> > -- Pavel Picka Red Hat
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
