locally yes, and you push that artefact
docker tags are not immutable, so YMMV on repeatability when someone runs the dockerfile later
they get away with it as for most software repeatable builds do not matter
but you can shuffle bad things into containers that way, by doing a back-and-forth tag switcheroo on the upstream tags you control
if you ever need to look into how to do such things properly, look into ’container promotion pipelines’ jfrog is one of the leading vendors
not super worried about it. Just trying to get the basics working.
https://github.com/snowblossomcoin/rosesnow/blob/main/docker/Dockerfile ``` FROM ubuntu:20.10 RUN apt-get update RUN apt-get install --yes curl gpg git apt-utils default-jdk maven RUN echo "deb [arch=amd64] http://storage.googleapis.com/bazel-apt stable jdk1.8" > /etc/apt/sources.list.d/snowblossom-bazel.list RUN curl https://bazel.build/bazel-release.pub.gpg | apt-key add - RUN apt-get update RUN apt-get install --yes bazel RUN mkdir -p /var/build/snow WORKDIR /var/build/snowblossom # TODO - make this cleaner, probably involving tags RUN git clone https://github.com/snowblossomcoin/rosesnow.git rosesnow.git WORKDIR /var/build/snowblossom/rosesnow.git RUN git pull && git checkout 1a5ee86c1eb16946011bdfb4d28ea6eaff6bb068 RUN bazel build :RoseSnow_deploy.jar WORKDIR /var/build/snowblossom/rosesnow.git/maven EXPOSE 8080/tcp RUN mvn package CMD mvn jetty:run # Run with: # docker run -p 8080:8080/tcp ```
any one submited this yet?
qtrade was added to coinmarketcap, but snow hasn't been verified yet
https://coinmarketcap.com/exchanges/qtrade/ qTrade trade volume and market listings
i think it will show up after it's verifed with all the correct infomation
same with https://www.coingecko.com/en/coins/snowblossom Get SnowBlossom (SNOW) price, charts, volume, market cap, exchange list and more.
any reason to start from a non-lts base? and there's a couple of optimisations one can do with the apt-get use (reduce intermediate layers, clean transient metadata out) - no big issues per se and that's not a multistage build - in a multistage build you'd actually not leave the development / build tools into the container
no accurate infomartion about snowblossom on the site
they also have a form for submiting information
@r i've relayed that onto discord as the more businessy types are there
there's this question: API endpoint that displays ONLY TOTAL SUPPLY as a NUMERICAL value (Type 'NA' if not applicable)(optional)
API endpoint that displays ONLY Circulating Supply as a numerical value(optional)
but it's optional
MUST be in this EXACT format - http://chainz.cryptoid.info/grs/api.dws?q=totalcoins. Total Supply refers to the # of coins in existence right now (minus any coins that have been verifiably burned.
and this :
Proof/Supporting evidence/documents Provide proof (e.g. imgur, gyazo) that the request is authentic (e.g. info is reflected on website, announcement thread, twitter page, etc.).
it seems complicated for adding asset on coinmarketcap
i have't looked at the form of coingecko yet
I might have to add an API to the explorer for that
yeah
The Rosetta API specifically requests ubuntu based builds
oh, now I understand your question
I just picked something with a high number
LTS would probably be smart
20.04 is LTS, right?
Anyways, I don't really care if this is a monster build. The only people running it will be exchanges and stuff looking to support snowblossom.
oh god, with 20.04 the apt-get install is interactive. ```Configuring tzdata ------------------ Please select the geographic area in which you live. Subsequent configuration questions will narrow this down by presenting a list of cities, representing the time zones in which they are located. 1. Africa 4. Australia 7. Atlantic 10. Pacific 13. Etc 2. America 5. Arctic 8. Europe 11. SystemV 3. Antarctica 6. Asia 9. Indian 12. US Geographic area:```
Api added