infisical.hellonext.co
Open in
urlscan Pro
76.76.21.142
Public Scan
Submitted URL: http://infisical.hellonext.co/
Effective URL: https://infisical.hellonext.co/
Submission: On November 24 via api from DK — Scanned from DK
Effective URL: https://infisical.hellonext.co/
Submission: On November 24 via api from DK — Scanned from DK
Form analysis
0 forms found in the DOMText Content
IInfisical Sign in / Sign up Boards Roadmap New Post Latest 1 CLI UPLOAD .ENV REQUIRES TYPE FOR EVERY KEY I have a .env file with over a hundred of variable, when I upload the file with CLI command, for each variable I need to type shared/personal. Is there any way I can batch assign shared or personal type or let use defined in the .env file itself? In Review•Feedback•0 1 ERROR: FAILED TO VALIDATE ENVIRONMENT After I logged in and connected to my workspace, I tried to push to development or pull from development, which I do not have any variables on Infisical yet. But both actions failed and got the message Error: Failed to validate environment In Review•Feedback•0 1 BROWSER TAB CRASH WHEN I UPLOAD .ENV FILE I’m uploading my development .env file with around 125 lines (no blank lines, no comments) but the browser tab always crashed after uploaded. Is there a limitation to the number of environment variables or other restrictions? In Review•Feedback•0 2 IT WOULD BE GREAT TO CREATE SORT OF REPOS IN EACH WORKSAPCE I have multiple clients and some of them have multiple applications. It would be awesome that I can group workspace by clients. Currently I name my workspace as follow “CLIENT_NAME/PROJET” In Review•Feature Requests•2 3 IT WOULD BE GREAT TO GROUP SOME ENVS BY SCOPE I mostly develop on monorepos and split back and front as micro services, so I have a lot of envs. Before infisical, I was able to add comments to my envs to split them visually by services. I do not think it is vital to have this in .env file, but it would be great in the infisical workspace. In Review•Feedback•2 Have something to say? Join the conversation. Boards Feedback4 Feature Requests1 Powered by Hellonext Loading...