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

update to latest ssb-server (again) #20

Merged
merged 8 commits into from
Mar 14, 2019
Merged

update to latest ssb-server (again) #20

merged 8 commits into from
Mar 14, 2019

Conversation

ahdinosaur
Copy link
Owner

@ahdinosaur ahdinosaur commented Feb 17, 2019

the last update didn't go so well, turns out this is a BREAKING CHANGE and pub owners will need to make some manual changes, i even tried to revert and then i ran into the errors that others have been encountering (#13, #15)

if anyone wants to help test this pull request (especially verifying my documentation changes are correct and helpful), that'd be rad! 😺

for a pub owner to update to the version in this pull request:

  1. build the image manually using this branch
  • git clone https://github.com/ahdinosaur/ssb-pub
  • cd ssb-pub
  • git checkout ssb-server
  • docker build -t ahdinosaur/ssb-pub .
  1. docker stop sbot
  2. docker rm sbot
  3. create ~/ssb-pub-data/config using the documentation in this pull request
  4. re-create ./create-sbot using the documentation in this pull request
  5. ./create-sbot

check things are working with docker logs sbot and ./sbot whoami

🌔

@@ -122,7 +141,7 @@ from GitHub:
```shell
git clone https://github.com/ahdinosaur/ssb-pub.git
cd ssb-pub
docker build -t ssb-pub .
docker build -t ahdinosaur/ssb-pub .

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't make sense for users. Accidental change?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hi @timjrobinson, this is on purpose, as you need to build an image with the same name as will be used in ./create-sbot, unless you change the image name there. even though it's namespaced with ahdinosaur, anyone should be able to build an image with that name, just not publish the image.

i made this change because when i first tested #19, i ran docker build -t ssb-pub then created a container with ahdinosaur/ssb-pub, so was actually running the old image and mistakenly thought the new image worked.

with the context, does this seem like an okay change?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah ok that makes sense to keep the scripts and documentation consistent no matter where you get the image from.

Dockerfile Outdated
@@ -11,13 +11,13 @@ ENV PATH=/home/node/.npm-global/bin:$PATH
ENV NPM_CONFIG_PREFIX=/home/node/.npm-global

USER node
RUN npm install -g [email protected]2
RUN npm install -g [email protected].2

EXPOSE 8008

HEALTHCHECK --interval=30s --timeout=30s --start-period=10s --retries=10 \
CMD sbot whoami || exit 1

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ssb-server whoami

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ssb-server still exports the sbot command, this is me being lazy but it should work.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't using sbot deprecated? IIRC it throws a warning when used. Might as well change it to set a good example for the community.

@@ -11,13 +11,13 @@ ENV PATH=/home/node/.npm-global/bin:$PATH
ENV NPM_CONFIG_PREFIX=/home/node/.npm-global

USER node
RUN npm install -g [email protected]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ssb-server is up to 14.1.6 now

@timjrobinson
Copy link

timjrobinson commented Mar 9, 2019

Thanks for fixing this! This works for me after applying the changes I mentioned.

@ahdinosaur ahdinosaur merged commit f661242 into master Mar 14, 2019
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 this pull request may close these issues.

2 participants