1. 25 Jul, 2020 3 commits
  2. 19 Jul, 2020 2 commits
    • Georges Racinet's avatar
      Enabling sshd by default for Heptapod · ba9d53983a7e
      Georges Racinet authored
      With our functional test suite performing various SSH tests,
      it's a pain for developers creating new workspaces regularly not
      to have it enabled by default.
      ba9d53983a7e
    • Georges Racinet's avatar
      Explicit HDK branch for Heptapod 0.14 · 78c3415de9cc
      Georges Racinet authored
      With Heptapod 0.15, we move to GitLab 13, which incurs
      a significantly different setup.
      
      It does not seem worth the effort to change the current
      default HDK branch to adapt to Heptapod 0.14, so let's
      have a branch.
      
      It's likely we'll have something similar at the next major
      version change, but we have a long time before that.
      78c3415de9cc
  3. 13 Jul, 2020 1 commit
  4. 11 Jul, 2020 1 commit
  5. 09 Jul, 2020 1 commit
  6. 08 Jul, 2020 4 commits
    • Georges Racinet's avatar
      README: specific HDK sections · b291fdd0207f
      Georges Racinet authored
      b291fdd0207f
    • Georges Racinet's avatar
      init make target · f139a89e0d33
      Georges Racinet authored
      This is intended to replace `gdk init`, but starting from within
      a HDK checkout. Needed because the first thing that `gdk init` does
      is a Git clone of the GDK main repo.
      
      We had to depend on `.ruby-version` so that gdk itself can run.
      This doesn't solve all chicken-and-eggs problem: we still depend
      on `rake` being available to produce `gdk-config.mk`.
      f139a89e0d33
    • Georges Racinet's avatar
      Ensure heptapod target is run before postgresql-seed-rails · af50b1dfdf8c
      Georges Racinet authored
      Currently, postgresql-seed-rails fails on the the 'projects' step.
      That wouldn't prevent developping Heptapod in itself, as long
      as the `heptapod` target is completed first.
      
      This artificial dependency can be removed once the seeding step
      succeeds, even if we simply make it smaller.
      af50b1dfdf8c
    • Georges Racinet's avatar
      Checkouting consistent revisions of Heptapod components · 19e50d7119c6
      Georges Racinet authored
      From the new `heptapod_series` setting in `gdk.yml` (defaulting to
      `default), a consistent list of revisions is derived in `config.rb`,
      dumped in the `gdk-config.mk` for final usage in `Makefile`.
      
      For now, since we don't have update capabilities, this will
      have to be set prior to the first call to `make`.
      
      The `stable` series is 0.13.x, a state of affairs that shouldn't
      stay for very long.
      19e50d7119c6
  7. 07 Jul, 2020 8 commits
    • Georges Racinet's avatar
      hgignore file · 907206a71d8f
      Georges Racinet authored
      derived from `.gitignore` with conversion of `/` patterns
      into rootglobs and addition of our own generated content.
      
      Probably a bit crude, does the job for now
      907206a71d8f
    • Georges Racinet's avatar
      Rebootstrap: fixing gettext dependency · fd0f737b5273
      Georges Racinet authored
      fd0f737b5273
    • Georges Racinet's avatar
      Rebootstrap: adding the hg-http service · 5e9a70b3e4c6
      Georges Racinet authored
      This completes making an entirely functional
      Heptapod Development Kit, although some things
      are still hardcoded.
      5e9a70b3e4c6
    • Georges Racinet's avatar
      39cf817e0a5a
    • Georges Racinet's avatar
      Rebootsrap: configuration for Mercurial and Gunicorn starter script · 54565e1688b1
      Georges Racinet authored
      This references the `hg` executable and the Mercurial configuration
      in the Rails app and Heptapod Shell configuration files.
      
      The `gunicorn-heptapod` script, the HTTP serving component for
      Mercurial content, wraps the `gunicorn` executable with the proper
      `HGRC_PATH`
      54565e1688b1
    • Georges Racinet's avatar
      Accepting Go 1.13 · 82cd76fc3008
      Georges Racinet authored
      Up to now, Go 1.13 has been working well enough for me for
      Heptapod development. Of course, switching to 1.14 will be
      advised, since the GDK insists on it, but that doesn't seem
      to be really necessary right now, we'll do it once the rest
      is ready.
      82cd76fc3008
    • Georges Racinet's avatar
      Rebootstrap: installing virtualenvs and py-heptapod · 498dbab50fa9
      Georges Racinet authored
      The new `py-heptapod` make target takes care of all of
      that.
      
      Then, of course, we'll need to generate the appropriate
      configurations to use it.
      498dbab50fa9
    • Georges Racinet's avatar
      Rebootstrap: checkouting Heptapod forked components · 19f030237776
      Georges Racinet authored
      We start from a fairly recent GDK version and change the source
      URLs for the Rails app, Heptapod Shell and Heptapod Workhorse.
      
      For now, we won't rename the cloned components to the
      more logical and clearer `heptapod`, `heptapod-shell` and `heptapod-workhorse`,
      because `gitlab/` is hardcoded a lot in the Makefile. And frankly,
      there are enough reasons for failure as it is: we'll do these renames
      only after we have a fully working kit.
      
      All Mercurial cloning is done through a share pool, whose
      path is for now hardcoded to the `hg-share-pool` sibling of the
      GDK root.
      
      We removed all `update` capabilities (will maybe make them work
      later) and have the `heptapod` (hardcoded) branch of each component
      checked out.
      Apart from that, we keep roughly the same logic as upstream GDK.
      
      At this point, `make` works up to the creation of the `root` user
      (`seed_fu`) and fails as expected on the creation of test
      projects - something we'll look at later.
      
      The Rails app starts, but the `Rails.root` had to be
      changed to just `root` in `lib/gitlab.rb` for background jobs to
      start, which means we may have something deeper to correct here.
      
      Of course, without the Python components (the next step), we won't go
      too far.
      19f030237776
  8. 01 Jun, 2020 5 commits
  9. 29 May, 2020 1 commit
  10. 01 Jun, 2020 1 commit
  11. 29 May, 2020 1 commit
  12. 01 Jun, 2020 4 commits
  13. 29 May, 2020 8 commits