Set up public HTTPS endpoint for RSKj #337
Labels
Clear labels
monitoring
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
service
discourse
Kosmos Community Forums
Infrastructure metrics, alerts, notifications, etc.
service
accounts
Kosmos Accounts
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
mastodon
kosmos.social
service
nostr
Relays, Blossom server, etc.
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
release
major
release
minor
release
patch
All your base are belong to us
User interface, process design, etc.
This won't be fixed
No labels
kredits-1
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#337
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds an nginx recipe with reverse proxy config and LE/certbot for
rsk-testnet.kosmos.org.refs #325
I added the WIP tag, because even though I think this should work just fine, converging the VM currently fails, claiming that the certbot resource method isn't available:
However, the
kosmos-nginxrecipe is included as usual, and the cookbook is also added as a dependency inmetadata.rb. I must have missed something, but at the moment I'm just blind as to what it could be.@greg Any chance you could have a quick look at this sometime soon?
I have merged the RSK mainnet PR, and updated this branch for the new
rsk-testnet-2node. So you can now run it as is against that one to reproduce the bug.Success! Our custom resource fix also works for this PR.
With
jqandcurlinstalled, you can get the block height from the testnet node like this e.g.:... now also for mainnet:
/cc @bumi
The port (4444) could be stored as in an attribute rather than just in the recipe, LGTM apart from that!