Adds cloud-init systemd HOWTO for lbrycrd on DigitalOcean. #48

Merged

EnigmaCurry merged 1 commit from cloud-init into master

2019-04-17 19:59:06 +02:00

EnigmaCurry commented

2019-04-17 05:37:14 +02:00

(Migrated from github.com)

This is a refactor of #45 that uses the main new lbrycrd Dockerfile. I've tested it, and it works.

Since this is now just a HOWTO, and no associated Dockerfile of its own, I think it makes sense to collect these sorts of things into a contrib folder. Is there a better idea out there?

This is a refactor of #45 that uses the main new lbrycrd Dockerfile. I've tested it, and it works. Since this is now just a HOWTO, and no associated Dockerfile of its own, I think it makes sense to collect these sorts of things into a contrib folder. Is there a better idea out there?

Leopere commented

2019-04-17 16:06:50 +02:00

(Migrated from github.com)

Can you make sure that this complies with the CONTRIBUTING.md I am especially interested in the Note to contributors section. Otherwise, I'm happy with this contribution getting merged.

Can you make sure that this complies with the [CONTRIBUTING.md](https://github.com/lbryio/lbry-docker/blob/master/CONTRIBUTING.md) I am especially interested in the [Note to contributors](https://github.com/lbryio/lbry-docker/blob/master/CONTRIBUTING.md#note-to-contributors) section. Otherwise, I'm happy with this contribution getting merged.

👍 1

EnigmaCurry commented

2019-04-17 19:33:53 +02:00

(Migrated from github.com)

Ok, I added the appopriate headers and a video. I figure the license and contributing sections of the main repo readme covers this as well, but if you think we need a link back to it, I can add it.

Leopere commented

2019-04-17 19:56:33 +02:00

(Migrated from github.com)

Ok, I added the appopriate headers and a video. I figure the license and contributing sections of the main repo readme covers this as well, but if you think we need a link back to it, I can add it.

What I'm going to do is accept this but you should assume no knowledge when you write a tutorial assume the "user is drunk but treat them as though they're not at the same time because they aren't."

Basically:

Tell people twice it never hurts to say it again so you don't have to say it again to everyone.
Never assume people know how to google things or use the search function so give them links back and forth to the documentation you have already written so that they don't have to look.

> Ok, I added the appopriate headers and a video. I figure the license and contributing sections of the main repo readme covers this as well, but if you think we need a link back to it, I can add it. What I'm going to do is accept this but you should assume no knowledge when you write a tutorial assume the "user is drunk but treat them as though they're not at the same time because they aren't." Basically: * Tell people twice it never hurts to say it again so you don't have to say it again to everyone. * Never assume people know how to google things or use the search function so give them links back and forth to the documentation you have already written so that they don't have to look.

Leopere (Migrated from github.com) approved these changes 2019-04-17 19:58:52 +02:00

No reviewers

Leopere

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-docker#48

No description provided.