CI/CD Pipeline #1

Closed
opened 2023-07-17 10:11:48 +02:00 by pratyush · 1 comment
Owner
pratyush added the due date 2023-07-18 2023-07-17 12:39:32 +02:00
pratyush added this to the SSG milestone 2023-07-17 12:39:32 +02:00
pratyush removed the due date 2023-07-18 2023-07-18 14:27:33 +02:00
Author
Owner

Random ideas:

  1. Consider local repo that one builds after conf and adding content.
  2. the public/ directory being in .gitignore suggests that:
    1. Upon completed git hook (appropriate) it will sorta trigger another actually public/ directory content repo to run its lint and validation tests.
    2. idk upon successful merge with master, it rsyncs the appropriate thing to the webserver (meh)
  3. Is it a good idea at all to jsut have one repo handling this logic and also potential django integration for backend.
Random ideas: 1. Consider local repo that one builds after conf and adding content. 2. the `public/` directory being in `.gitignore` suggests that: i. Upon completed git hook (appropriate) it will sorta trigger another actually `public/` directory content repo to run its lint and validation tests. ii. idk upon successful merge with master, it rsyncs the appropriate thing to the webserver (meh) 3. Is it a good idea at all to jsut have one repo handling this logic and also potential django integration for backend.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: pratyush/website#1
No description provided.