Add subdomain for easy access #348
Comments
|
it is pretty awesome it already shows up at the first result on google when searching "polkadot faucet" though :D |
|
@lovelaced @itsbirdo may be instead of polkadot.network we could have it like faucets.parity.io? that would be fair and yet easier From the SEO perspective faucet could be adjusted to respond on "polkadot faucet" requests in google, so should be fine IMO |
|
@lovelaced @itsbirdo i guess if no one against it so far, so I will prepare PR to deploy this to faucets.parity.io until we have more clarity about *.polkadot.network. If we have more info there - then there will be no problem to 301 redirect to a better domain |
|
@mordamax, I suggest to use |
|
Works for me! |
|
I'm looking forward to it 🤩 I don't know who manages the webadmin for polkadot.io, but setting it up would be as simple as setting the custom domain in the pages configuration and then configuring the DNS. |
Merged
Bullrich
added a commit
that referenced
this issue
Mar 20, 2024
This removes the base url, making the website work on the root of the domain. Also, by doing this change, and having set up the dns, this resolves #348
|
New webiste has been configured by @mordamax! Find the faucet in faucet.polkadot.io |
|
Birdo's announcement here: https://twitter.com/itsbirdo_/status/1770422620095193370 Excellent job team!! 🚀 |
forgetso
added a commit
to prosopo/polkadot-testnet-faucet
that referenced
this issue
Mar 26, 2024
* lockfile update * Upgrade deps * Package-lock.json * Updating e2e tests readme (paritytech#375) * Fixing e2e readme link * Adding runtimeRestarter (paritytech#376) Fixes paritytech#223 + Adding prom-client dependency, because it was removed from @eng-automation/js (rightfully so) * Updating zombinenet verion in e2e docs (paritytech#378) @josepot has reported an error with `@zombienet/cli@1.3.43`, while the latest version worked * Using PAPI for e2e tests (paritytech#379) * Currently, e2e types are generated on postinstall and prebuild steps, which requires metadata to be available in Docker image, even though it's not technically used in the application code. I think separating things would make things more complicated, but it's possible. * Couldn't undestand the reason for having two different COPY instructions in Dockerfile, but that doesn't live well with generating types in postinstall, so merging those two * .scale metadata files from Zombienet hosts saved in the codebase, in order to be able to compile the code separately from running Zombienet * Update dependencies * yarn.lock * Bump the npm_and_yarn group across 2 directories with 2 updates (paritytech#381) * removed base url (paritytech#382) This removes the base url, making the website work on the root of the domain. Also, by doing this change, and having set up the dns, this resolves paritytech#348 * Update deps * Update API calls * Silence polkadot API type errors * Update captcha type to image and set width of captcha container * remove grid class * switch back to PJS. change port number * remove prettier deps * update port * set procaptcha details * fix dropdown z-index * Fix z-indexes * Change mock provider version * remove console.errors --------- Co-authored-by: Yuri Volkov <0@mcornholio.ru> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Javier Bullrich <javier@bullrich.dev>
forgetso
added a commit
to prosopo/polkadot-testnet-faucet
that referenced
this issue
Apr 29, 2024
* Updating e2e tests readme (paritytech#375) * Fixing e2e readme link * Adding runtimeRestarter (paritytech#376) Fixes paritytech#223 + Adding prom-client dependency, because it was removed from @eng-automation/js (rightfully so) * Updating zombinenet verion in e2e docs (paritytech#378) @josepot has reported an error with `@zombienet/cli@1.3.43`, while the latest version worked * Using PAPI for e2e tests (paritytech#379) * Currently, e2e types are generated on postinstall and prebuild steps, which requires metadata to be available in Docker image, even though it's not technically used in the application code. I think separating things would make things more complicated, but it's possible. * Couldn't undestand the reason for having two different COPY instructions in Dockerfile, but that doesn't live well with generating types in postinstall, so merging those two * .scale metadata files from Zombienet hosts saved in the codebase, in order to be able to compile the code separately from running Zombienet * Bump the npm_and_yarn group across 2 directories with 2 updates (paritytech#381) * removed base url (paritytech#382) This removes the base url, making the website work on the root of the domain. Also, by doing this change, and having set up the dns, this resolves paritytech#348 * Added markup code generation (paritytech#383) It generates a JSON object inside the header following the instructions from: https://developers.google.com/search/docs/appearance/structured-data/faqpage It parses the information of the markdown text to generate this json object. This resolves paritytech#277 * Updated actions to latest and added retention period (paritytech#384) We currently don't have an artifact retention period, so it defaults to 90 days. While the artifact for the site is not too big, having one build per push and PR can quickly accumulate the amount and make us hit our hard limit. By adding a limit to the retention day of 5 days we ensure that we get rid of the old artifacts faster than waiting for two whole months. I also updated all the actions version to latest release * Bump the npm_and_yarn group across 1 directory with 1 update (paritytech#385) * Bump the npm_and_yarn group across 1 directory with 1 update (paritytech#387) * Update Frequency Faucet URL (paritytech#393) As the Frequency Faucet now also supports Frequency Paseo testnet in addition to the Rococo one, the url is being set to a generic one instead of specific for the network. https://faucet.testnet.frequency.xyz/ * moved tag-client to work in pull_request_target (paritytech#394) It fails when an external contributors make a PR. This will fix that issue. * Merge latest upstream and use a transaction queue to send txs to nodes * Add MIT LICENSE (paritytech#395) * bump to polkadot 10.13.1 * lockfile * yarn.lock * yarn.lock * yarn.lock * yarn.lock * yarn.lock client * Fix test mock * Add @polkadot/util to dev dependencies * Address comments from @mutantcornholio --------- Co-authored-by: Yuri Volkov <0@mcornholio.ru> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Javier Bullrich <javier@bullrich.dev> Co-authored-by: Wil Wade <wil@wilwade.com> Co-authored-by: Maksym H <1177472+mordamax@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Faucet Type
Web
Problem
It would be great if we can add a subdomain to the faucet for easy access - this will improve the ability for developers to be able to remember the faucet address.
Suggestion:
faucet.polkadot.network
cc: @Bullrich
Address
No response
Network ID
Relay Chain
Relevant log output
No response
The text was updated successfully, but these errors were encountered: