github-starred/flowsint
2
0
Fork 0
mirror of https://github.com/reconurge/flowsint.git synced 2026-05-07 04:09:49 -05:00
Code Issues 264 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #66] make prod and make dev to fail because it tries to copy .env.example files that are not present. #60

New Issue
Closed
opened 2026-04-11 08:41:24 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-11 08:41:24 -05:00
Owner
Copy Link

Originally created by @abdulhafeez1724 on GitHub (Nov 18, 2025).
Original GitHub issue: https://github.com/reconurge/flowsint/issues/66

The current version of Flowsint uses a single unified .env file at the project root.
However, the Makefile still references old paths (flowsint-api/.env, flowsint-core/.env, flowsint-app/.env)
that no longer exist in the updated project structure.

This causes make prod and make dev to fail because it tries to copy .env.example files that are not present.

Originally created by @abdulhafeez1724 on GitHub (Nov 18, 2025). Original GitHub issue: https://github.com/reconurge/flowsint/issues/66 The current version of Flowsint uses a single unified .env file at the project root. However, the Makefile still references old paths (flowsint-api/.env, flowsint-core/.env, flowsint-app/.env) that no longer exist in the updated project structure. This causes `make prod` and `make dev` to fail because it tries to copy .env.example files that are not present.
GiteaMirror commented 2026-04-11 08:41:25 -05:00
Author
Owner
Copy Link

@dextmorgn commented on GitHub (Nov 18, 2025):

Hey @abdulhafeez1724,

Could you show some errors messages ?

Cause it seems what you're describing is the expected behavior, as the .env at the root is copied to other directories on make commands

<!-- gh-comment-id:3545690278 --> @dextmorgn commented on GitHub (Nov 18, 2025): Hey @abdulhafeez1724, Could you show some errors messages ? Cause it seems what you're describing is the expected behavior, as the `.env` at the root is copied to other directories on make commands
GiteaMirror commented 2026-04-11 08:41:25 -05:00
Author
Owner
Copy Link

@abdulhafeez1724 commented on GitHub (Nov 18, 2025):

@dextmorgn
repo is using the new unified configuration model: one .env file at the root, not separate .env files in each module.

The Makefile is still referencing old paths (flowsint-api/.env, etc.), which no longer exist in your version — that's why you saw:

cp: cannot stat '/home/.../.env.example': No such file or directory

<!-- gh-comment-id:3545707158 --> @abdulhafeez1724 commented on GitHub (Nov 18, 2025): @dextmorgn repo is using the new unified configuration model: one .env file at the root, not separate .env files in each module. The Makefile is still referencing old paths (flowsint-api/.env, etc.), which no longer exist in your version — that's why you saw: cp: cannot stat '/home/.../.env.example': No such file or directory
GiteaMirror commented 2026-04-11 08:41:25 -05:00
Author
Owner
Copy Link

@dextmorgn commented on GitHub (Nov 18, 2025):

that's why you saw: cp: cannot stat '/home/.../.env.example': No such file or directory

Not sure what you're refering to, where did you see this error ?

flowsint-api/.env, flowsint-app/.env, etc are valid paths and there need to be a .env file in each of these directories. They indeed don't exist by default

<!-- gh-comment-id:3545852315 --> @dextmorgn commented on GitHub (Nov 18, 2025): > that's why you saw: cp: cannot stat '/home/.../.env.example': No such file or directory Not sure what you're refering to, where did you see this error ? `flowsint-api/.env`, `flowsint-app/.env`, etc are valid paths and there need to be a .env file in each of these directories. They indeed don't exist by default
GiteaMirror commented 2026-04-11 08:41:25 -05:00
Author
Owner
Copy Link

@abdulhafeez1724 commented on GitHub (Nov 18, 2025):

yes by defaul they not exist and for that we must change the
makefile to this (makefile was looking the .env in each module so i changed)
thanks

Image
<!-- gh-comment-id:3545916032 --> @abdulhafeez1724 commented on GitHub (Nov 18, 2025): yes by defaul they not exist and for that we must change the makefile to this (makefile was looking the .env in each module so i changed) thanks <img width="1752" height="527" alt="Image" src="https://github.com/user-attachments/assets/c63f81f0-dfc4-4f3b-b787-c40cd7103c36" />
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
documentation
enhancement
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/flowsint#60
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?