Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(mainnet) migration of all ecosystems projects on DeWeb #141

Closed
SlnPons opened this issue Oct 18, 2024 · 13 comments
Closed

(mainnet) migration of all ecosystems projects on DeWeb #141

SlnPons opened this issue Oct 18, 2024 · 13 comments
Assignees
Labels

Comments

@SlnPons
Copy link
Collaborator

SlnPons commented Oct 18, 2024

Objective
Migrate internal porjects on mainnet

How to

@pivilartisant
Copy link
Collaborator

pivilartisant commented Oct 18, 2024

@pivilartisant
Copy link
Collaborator

landing page MS
bridge FE
explorer FE
syntra
massa.net
massa.foundation
mns
vesting
docs

@SlnPons
Copy link
Collaborator Author

SlnPons commented Oct 22, 2024

  • Who we'll pay the fees?
  • How we'll do that exactly?

@pivilartisant
Copy link
Collaborator

  • Who we'll pay the fees?

    • How we'll do that exactly?

also migrating once is good, but if it's better if we add github action flows to update the builds at each merge

@pivilartisant
Copy link
Collaborator

define process to add to massa provider allowlist

@SlnPons
Copy link
Collaborator Author

SlnPons commented Oct 28, 2024

  • Who we'll pay the fees?

    • How we'll do that exactly?

also migrating once is good, but if it's better if we add github action flows to update the builds at each merge

What was the conclusion when we discuss this point? I can't remember

@SlnPons
Copy link
Collaborator Author

SlnPons commented Oct 28, 2024

define process to add to massa provider allowlist

@thomas-senechal could you specify (again) how the allowlist will work in this 1st phase please?
Because indeed, I think we should describe how it works on the doc (for our ecosystem but also for partners). wdyt?

@pivilartisant
Copy link
Collaborator

  • Who we'll pay the fees?

    • How we'll do that exactly?

also migrating once is good, but if it's better if we add github action flows to update the builds at each merge

What was the conclusion when we discuss this point? I can't remember

Should appear in milestone 3 roadmap as added feature

@thomas-senechal
Copy link
Member

define process to add to massa provider allowlist

@thomas-senechal could you specify (again) how the allowlist will work in this 1st phase please? Because indeed, I think we should describe how it works on the doc (for our ecosystem but also for partners). wdyt?

Are the explainations here enough ? 🤔
https://docs.massa.net/docs/deweb/local-server-config/server-config#configuration-fields

@pivilartisant
Copy link
Collaborator

Image

Image

@pivilartisant pivilartisant changed the title Organise the migration of all ecosystems projects on DeWeb (mainnet) migration of all ecosystems projects on DeWeb Nov 6, 2024
@pivilartisant pivilartisant reopened this Nov 6, 2024
@SlnPons SlnPons added the p1 label Nov 21, 2024
@damip
Copy link
Member

damip commented Nov 21, 2024

It would be important I think to have a CI system to automatically deploy sites on deweb from github (eg. to avoid having an older version of the docs in there)

@pivilartisant
Copy link
Collaborator

It would be important I think to have a CI system to automatically deploy sites on deweb from github (eg. to avoid having an older version of the docs in there)

The issue is part of our milestone 3

@pivilartisant
Copy link
Collaborator

pivilartisant commented Nov 27, 2024

@SlnPons SlnPons closed this as completed Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants