update alpha beta URLs

Author: Aniket-Engg

apps/remix-ide/release-process.md

@@ -1,6 +1,6 @@
 This document describes:
  - how to update remix.ethereum.org.
- - how to update remix-alpha.ethereum.org.
+ - how to update alpha.remix.live
  - how to release remix IDE.
 
 # Remix IDE Release
@@ -47,7 +47,7 @@ This is not strictly speaking a release. Updating the remix site is done through
 
  CircleCI will build automatically and remix.ethereum.org will be updated
 
-# remix-alpha.ethereum.org update
+# alpha.remix.live update
 
-remix-alpha.ethereum.org is automatically updated every time commits are pushed to master
+alpha.remix.live is automatically updated every time commits are pushed to master
 

apps/remix-ide/src/app.ts

@@ -224,8 +224,8 @@ class AppComponent {
     this.engine.register(appManager)
 
     const matomoDomains = {
-      'remix-alpha.ethereum.org': 27,
-      'remix-beta.ethereum.org': 25,
+      'alpha.remix.live': 27,
+      'beta.remix.live': 25,
       'remix.ethereum.org': 23,
       '6fd22d6fe5549ad4c4d8fd3ca0b7816b.mod': 35 // remix desktop
     }

apps/remix-ide/src/app/tabs/locales/en/remixd.json

@@ -7,7 +7,7 @@
   "remixd.text1": "Access your local file system from Remix IDE using <a>Remixd NPM package</a>.",
   "remixd.text2": "Remixd <a>documentation</a>.",
   "remixd.text3": "The remixd command is:",
-  "remixd.text4": "The remixd command without options uses the terminal's current directory as the shared directory and the shared Remix domain can only be https://remix.ethereum.org, https://remix-alpha.ethereum.org, or https://remix-beta.ethereum.org",
+  "remixd.text4": "The remixd command without options uses the terminal's current directory as the shared directory and the shared Remix domain can only be https://remix.ethereum.org, https://alpha.remix.live, or https://beta.remix.live",
   "remixd.text5": "Example command with flags:",
   "remixd.text6": "For info about ports, see <a>Remixd ports usage</a>",
   "remixd.text7": "This feature is still in Alpha. We recommend to keep a backup of the shared folder.",

apps/remix-ide/src/assets/js/loader.js

@@ -1,12 +1,12 @@
 const domains = {
-  'remix-alpha.ethereum.org': 27,
-  'remix-beta.ethereum.org': 25,
+  'alpha.remix.live': 27,
+  'beta.remix.live': 25,
   'remix.ethereum.org': 23,
   'localhost': 35 // remix desktop
 }
 const domainsOnPrem = {
-  'remix-alpha.ethereum.org': 1,
-  'remix-beta.ethereum.org': 2,
+  'alpha.remix.live': 1,
+  'beta.remix.live': 2,
   'remix.ethereum.org': 3,
   'localhost': 4 // remix desktop
 }

apps/remix-ide/team-best-practices.md

@@ -12,8 +12,8 @@ Related links:
  - Public WebSite: https://remix-project.org
  - Remix basic FAQ: https://hackmd.io/KVooMJhWRImCGq6zkDgW9A
  - Remix live: https://remix.ethereum.org
- - Remix alpha live: https://remix-alpha.ethereum.org
- - Remix beta live: https://remix-beta.ethereum.org
+ - Remix alpha live: https://alpha.remix.live
+ - Remix beta live: https://beta.remix.live
  - Remix-lib NPM module: https://www.npmjs.com/package/@remix-project/remix-lib
  - Remix-tests NPM module: https://www.npmjs.com/package/@remix-project/remix-tests
  - Remix-solidity NPM module: https://www.npmjs.com/package/@remix-project/remix-solidity
@@ -114,7 +114,7 @@ Before starting to coding, we should ensure all devs / contributors are aware of
  ### 3) Merge:
 
  - Merging is possible after Review and Tests are ok and when the PR is approved.
- - After a merge, it is highly recommended to check the new code in `remix-alpha.ethereum.org`
+ - After a merge, it is highly recommended to check the new code in `alpha.remix.live`
 
 ---
 
@@ -195,8 +195,8 @@ Before starting to coding, we should ensure all devs / contributors are aware of
 ### release process:
 
  - We release an `x.0.0` if there's a fundamental change in our UX design, which means users will need to readapt the way they use the app
- - after a week finishes, we publish/release a new version as **remix-beta.ethereum.org** and inform users so early adopters can test. after another week, when the next finished work is released as **remix-beta.ethereum.org**, the previous one becomes **remix.ethereum.org** and all users can start using it
- - a bot to automatically notify users about upcoming features on all channels whenever **remix-beta.ethereum.org** is updated
+ - after a week finishes, we publish/release a new version as **beta.remix.live** and inform users so early adopters can test. after another week, when the next finished work is released as **beta.remix.live**, the previous one becomes **remix.ethereum.org** and all users can start using it
+ - a bot to automatically notify users about upcoming features on all channels whenever **beta.remix.live** is updated
  - in case it's a major version increase - this announcement should be specially marked so people can check early instead of being confronted with drastic changes when **remix.ethereum.org** updates
 ### maintenance:
  - Setting up a "bug" time where we each take a bug for which:

libs/remix-ui/app/src/lib/remix-app/components/modals/origin-warning.tsx

@@ -11,7 +11,7 @@ const OriginWarning = () => {
     if (window.location.hostname === 'yann300.github.io') {
       setContent('This UNSTABLE ALPHA branch of Remix has been moved to http://ethereum.github.io/remix-live-alpha.')
     } else if (
-      window.location.hostname === 'remix-alpha.ethereum.org' ||
+      window.location.hostname === 'alpha.remix.live' ||
       (window.location.hostname === 'ethereum.github.io' && window.location.pathname.indexOf('/remix-live-alpha') === 0)
     ) {
       setContent('Welcome to the Remix alpha instance. Please use it to try out latest features. But use preferably https://remix.ethereum.org for any production work.')

libs/remix-ui/home-tab/src/lib/components/constant.ts

@@ -1,6 +1,6 @@
 const branches = {
-  'remix-beta.ethereum.org': 'beta',
-  'remix-alpha.ethereum.org': 'alpha',
+  'beta.remix.live': 'beta',
+  'alpha.remix.live': 'alpha',
   'remix.ethereum.org': 'live'
 }
 

libs/remixd/README.md

@@ -33,7 +33,7 @@ If you were using the old one you need to:
 
 ## remixd command
 
-The remixd command without options shares present working directory and the shared Remix domain will be https://remix.ethereum.org, https://remix-alpha.ethereum.org, or https://remix-beta.ethereum.org
+The remixd command without options shares present working directory and the shared Remix domain will be https://remix.ethereum.org, https://alpha.remix.live, or https://beta.remix.live
 
 The remixd command is:
 ```

libs/remixd/origins.json

@@ -1,10 +1,10 @@
 {
     "data":[
-        "http://remix-alpha.ethereum.org",
-        "http://remix-beta.ethereum.org",
+        "http://alpha.remix.live",
+        "http://beta.remix.live",
         "http://remix.ethereum.org",
-        "https://remix-alpha.ethereum.org",
-        "https://remix-beta.ethereum.org",
+        "https://alpha.remix.live",
+        "https://beta.remix.live",
         "https://remix.ethereum.org",
         "package://a7df6d3c223593f3550b35e90d7b0b1f.mod",
         "package://6fd22d6fe5549ad4c4d8fd3ca0b7816b.mod",

release-process.md

@@ -5,11 +5,11 @@ This document includes the release instructions for:
  - Publishing `remixd` to NPM
  - Publishing remix libraries to NPM
  - Updating Remix's live version on remix.ethereum.org
- - Updating Remix's alpha version on remix-alpha.ethereum.org
- - Updating Remix's beta version on remix-beta.ethereum.org
+ - Updating Remix's alpha version on `alpha.remix.live`
+ - Updating Remix's beta version on `beta.remix.live`
 
 ## Feature Freeze
-Once feature freeze is done, `remix_beta` should be updated to the latest master which will automatically update `remix-beta.ethereum.org` through a CI job.
+Once feature freeze is done, `remix_beta` should be updated to the latest master which will automatically update `beta.remix.live` through a CI job.
 
 Use this unified command:
 
@@ -23,7 +23,7 @@ or individually:
  - `git push -f origin remix_beta`
 
 ## Testing
-Testing is performed after the Feature Freeze on `remix-beta.ethereum.org`. `build-qa-doc.js` script can be used to generate the list of QA tasks. Instructions to use the file are given in the file itself: https://github.com/ethereum/remix-project/blob/master/build-qa-doc.js#L18 
+Testing is performed after the Feature Freeze on `beta.remix.live`. `build-qa-doc.js` script can be used to generate the list of QA tasks. Instructions to use the file are given in the file itself: https://github.com/ethereum/remix-project/blob/master/build-qa-doc.js#L18 
 
 Once ready to run, it can be run using the Node.js: `node build-qa-doc.js`
 
@@ -141,4 +141,4 @@ or individually:
 
 ## Remix IDE Alpha Release
 
-remix-alpha.ethereum.org is automatically updated every time a commit is pushed to `master` branch
+`alpha.remix.live` is automatically updated every time a commit is pushed to `master` branch