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

Develop Nix configuration for frontend #188

Closed
2 of 3 tasks
Tracked by #167
placek opened this issue Feb 16, 2024 · 1 comment · Fixed by #448
Closed
2 of 3 tasks
Tracked by #167

Develop Nix configuration for frontend #188

placek opened this issue Feb 16, 2024 · 1 comment · Fixed by #448

Comments

@placek
Copy link
Contributor

placek commented Feb 16, 2024

As a frontend developer,

I want to create a Nix configuration for the frontend module,

So that the build and deployment process is aligned with the backend and optimized.

Acceptance Criteria:

  • A Nix configuration for the frontend module is developed.
  • The configuration mirrors the backend setup and dependencies.
  • Development environments are explicitly defined, including all necessary dependencies and toolchains.
@placek placek mentioned this issue Feb 16, 2024
14 tasks
@placek placek self-assigned this Feb 16, 2024
@placek placek removed the Sprint 1 label Feb 16, 2024
@placek placek removed the 📜 Documentation Improvements or additions to documentation label Feb 19, 2024
placek added a commit that referenced this issue Mar 7, 2024
Removed obsolete Nix configuration files (default.nix, node-env.nix, and
node-packages.nix) from the frontend module. This change is part of a
broader effort to update and realign the frontend's build and deployment
process with the backend's, ensuring a more streamlined and optimized
development environment. The removal of these files paves the way for
introducing a revised and more efficient Nix setup that better mirrors
the backend's configuration and fulfills the specified acceptance
criteria for development environments and dependencies.
placek added a commit that referenced this issue Mar 7, 2024
This commit introduces a new yarn2nix based package definition for the
frontend application. By adding this Nix expression, developers can
easily incorporate the project into their nix-shell based environment.

Changes:
- Added a new file `govtool/frontend/default.nix` that defines the
  yarn2nix based package configuration for the frontend application
  "govtool-frontend". This file includes settings for the project name,
  source directory, package.json file, and yarn.lock file wrapped in the
  `mkYarnPackage` function, enabling developers to utilize the project
  seamlessly in their nix-shell based environments.
placek added a commit that referenced this issue Mar 12, 2024
Developed Nix shell configurations for both frontend and backend modules
to streamline the build and deployment processes and ensure alignment
with backend setup and dependencies. The new shell configurations
provide necessary tools and dependencies for development environments,
optimizing the overall development workflow.

Changes:
- Updated govtool/backend/default.nix to simplify package retrieval
  using `<nixpkgs>` and removed unnecessary sources file inclusion.
- Created govtool/backend/shell.nix to define additional dependencies
  like awscli, docker, git, and gnumake for the backend module.
- Added govtool/frontend/shell.nix to specify frontend module
  dependencies, ensuring consistency with the backend setup.
placek added a commit that referenced this issue Mar 12, 2024
…guration-for-frontend

[#188] Develop NIX configuration for frontend
@pmbinapps
Copy link

No break on test-sancho.
Also already on Stage after last PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants