Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restructure readme: prefer containerized workflow #38

Closed
NickVolynkin opened this issue Mar 1, 2023 · 0 comments · Fixed by #36
Closed

Restructure readme: prefer containerized workflow #38

NickVolynkin opened this issue Mar 1, 2023 · 0 comments · Fixed by #36

Comments

@NickVolynkin
Copy link
Contributor

There's no need to go all the way with dependencies in the container-based workflow.

  • Put containter-based workflow to the top.
  • Add table of contents.
  • Run through the workflow with a real developer from the community.
NickVolynkin added a commit that referenced this issue Jun 19, 2023
* Build an image with compiled toolchain:
  `ghcr.io/nilfoundation/proof-market-toolchain:latest`.
  It has everything to start working with the toolchain right away.
  Releases are made from a secured machine, not CI.
  However, the image is built on each commit to check that it stays
  buildable.

* Use a base build image with dependencies, including Boost 1.76.0.
  Using the base image speeds up builds a lot.

* Update readme. Encourage users to take the `:latest` image rather
  than build it themselves when they just need to use the toolchain.

* Renew build instructions: now git operations, dependencies, and build
  instructions for two different modes are grouped together.

Resolve #35
Resolve #38
NickVolynkin added a commit that referenced this issue Jun 19, 2023
* Build an image with compiled toolchain:
  `ghcr.io/nilfoundation/proof-market-toolchain:latest`.
  It has everything to start working with the toolchain right away.
  Releases are made from a secured machine, not CI.
  However, the image is built on each commit to check that it stays
  buildable.

* Use a base build image with dependencies, including Boost 1.76.0.
  Using the base image speeds up builds a lot.

* Update readme. Encourage users to take the `:latest` image rather
  than build it themselves when they just need to use the toolchain.

* Renew build instructions: now git operations, dependencies, and build
  instructions for two different modes are grouped together.

Resolve #35
Resolve #38
NickVolynkin added a commit that referenced this issue Jun 19, 2023
* Build an image with compiled toolchain:
  `ghcr.io/nilfoundation/proof-market-toolchain:latest`.
  It has everything to start working with the toolchain right away.
  Releases are made from a secured machine, not CI.
  However, the image is built on each commit to check that it stays
  buildable.

* Use a base build image with dependencies, including Boost 1.76.0.
  Using the base image speeds up builds a lot.

* Update readme. Encourage users to take the `:latest` image rather
  than build it themselves when they just need to use the toolchain.

* Renew build instructions: now git operations, dependencies, and build
  instructions for two different modes are grouped together.

Resolve #35
Resolve #38
NickVolynkin added a commit that referenced this issue Jun 20, 2023
* Build an image with compiled toolchain:
  `ghcr.io/nilfoundation/proof-market-toolchain:latest`.
  It has everything to start working with the toolchain right away.
  Releases are made from a secured machine, not CI.
  However, the image is built on each commit to check that it stays
  buildable.

* Use a base build image with dependencies, including Boost 1.76.0.
  Using the base image speeds up builds a lot.

* Update readme. Encourage users to take the `:latest` image rather
  than build it themselves when they just need to use the toolchain.

* Renew build instructions: now git operations, dependencies, and build
  instructions for two different modes are grouped together.

Resolve #35
Resolve #38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant