Skip to content

Conversation

@jinhojang6
Copy link
Contributor

@jinhojang6 jinhojang6 commented Dec 3, 2025

The backend URL was updated so changed it to 'https://admin-acid.logos.co/api'

Preview: https://contribute-logos-co-git-update-api-endpoint-acidinfo.vercel.app/en/proposals/

@vercel
Copy link

vercel bot commented Dec 3, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
contribute-logos-co Ready Ready Preview Comment Dec 3, 2025 11:46am

@jinhojang6 jinhojang6 requested a review from a team December 3, 2025 11:49
Copy link
Contributor

@JulesFiliot JulesFiliot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested & working :shipit:

@github-project-automation github-project-automation bot moved this from In Progress to Waiting in Web & User Interfaces Dec 4, 2025
}

export function getContributeApiBase() {
return 'https://dev-admin-acid.logos.co/api'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't develop/local still point to dev domain?

Copy link
Contributor Author

@jinhojang6 jinhojang6 Dec 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@felicio Good point, and I didn't notice it at first.

But this project is purely a frontend that consumes the admin-acid API, so I think using a .env file for the base URL could be unnecessary. (FYI, this project uses static exports without node.js and is deployed by caddy, and the Logos website is using node.js)

Also, the infra team deployed it through Jenkins, and there was no .env file configuration during the initial setup.

But if you think it would be better to manage the base URL through a .env file, let me add one and coordinate with the infra team about the deployment process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants