What to treat as 'source'

10 views
Skip to first unread message

Michael Powell

unread,
Feb 17, 2022, 7:16:18 PM2/17/22
to django...@googlegroups.com
Hello,

Perhaps a general CMS related topic... What (necessarily, 'how') do we treat as source code? If we have a Django or an OrchardCore/CMS, for example. The infrastructure, obviously, i.e. the framework, intermediate derivations, etc. What about any authoring efforts, milestones, versioning, etc? Similarly, where/when are the authoring efforts usually done? As part of 'dev' inner loop? Or might there also be an author inner/outer loop? Then with whatever corresponding database backups, migrations, etc.

Thank you...

Best regards,

Michael W. Powell

Shaheed Haque

unread,
Feb 18, 2022, 2:34:38 AM2/18/22
to django...@googlegroups.com
On Fri, 18 Feb 2022 at 00:16, Michael Powell <mwpow...@gmail.com> wrote:
>
> Hello,
>
> Perhaps a general CMS related topic... What (necessarily, 'how') do we treat as source code? If we have a Django or an OrchardCore/CMS, for example. The infrastructure, obviously, i.e. the framework, intermediate derivations, etc. What about any authoring efforts, milestones, versioning, etc? Similarly, where/when are the authoring efforts usually done? As part of 'dev' inner loop? Or might there also be an author inner/outer loop? Then with whatever corresponding database backups, migrations, etc.

I think of it like this:

- Starting with "If I were to try to do a release of my product, what
files would I need?"
- Subtract, or rather separate out, any credentials since live
credentials won't be in checked-in source.
- Add in any files and artefacts needed to run tests.
- Add in anything needed to deploy the product.
- Add in any source for documentation, either customer facing or
internal specs/procedures.
- Some special consideration may be needed for large binary objects.

All that belongs in the source control system, meaning that it is
backed up along with development history/comments. Note that this is
essentially independent of whether the product is software: it could
just as easily be the design for an ASIC, or a marketing website.

End-user data is NOT part of the source (it should be backed up of
course, but not in the source control system).

Does that help?

Thanks, Shaheed

> Thank you...
>
> Best regards,
>
> Michael W. Powell
>
> --
> You received this message because you are subscribed to the Google Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAM%3DaUXoVdL4RgHbS6dk7mw-dB6n7SBcx3g5Q0RiJhRG_GTuTeQ%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages