![]() ![]() To build the frontend client without watching for changes, you can use: All available tasks can be found in `package.json` under _scripts_. We use these technologies for our FE build process to allow us to use modules, es6 syntax, and css variables.įrontend tasks are executed using `yarn`. Leiningen will automatically fetch Clojure dependencies when needed, but for JavaScript dependencies you'll need to kick off the installation process manually when needed. Metabase depends on lots of other 3rd party libraries to run, so as you are developing you'll need to keep those up to date. a frontend written as a Javascript single-page application which provides the web UI.īoth components are built and assembled together into a single jar file which runs the entire application. a backend written in Clojure which contains a REST API as well as all the relevant code for talking to databases and processing queries.Ģ. The Metabase application has two basic compnents:ġ. If you plan to work on the Metabase code and make changes then you'll need to understand a few more things. There is a script which will execute all steps in the process and output the final artifact for you.Īfter running the build script simply look in `target/uberjar` for the output. ![]() jar file which can run on any modern JVM. The entire Metabase application is compiled and assembled into a single. If you are developing on Windows, make sure to use Ubuntu on Windows and follow instructions for Ubuntu/Linux instead of installing ordinary Windows versions. Follow the links to download and install them on your own before continuing. These are the set of tools which are required in order to complete any build of the Metabase code. As an example, Node dependencies installed in normal Windows environment will not work inside Ubuntu Bash environment. ![]() If you have problems with your development environment, make sure that you are not using any development commands outside the Bash shell. The Ubuntu Bash shell works well for both backend and frontend development. The development scripts are designed for Linux/Mac environment, so we recommend using the latest Windows 10 version with () and (). We don't like getting sued, so before merging any pull request, we'll need each person contributing code to sign a Contributor License Agreement () ![]() The point is not to generate documentation but to allow discussion to reference a specific proposed design and to allow others to consider the implications of a given design. The goals of this document are to make explicit the assumptions, constraints and tradeoffs any given feature implementation will contain. Any feature that requires a major decision to be reached will need to have an explicit design document written. Each pull request should address a single issue, and contain both the fix as well as a description of how the pull request and tests that validate that the PR fixes the issue in question.įor significant feature additions, it is expected that discussion will have taken place in the attached issue. In general, we like to have an open issue for every pull request as a place to discuss the nature of any bug or proposed improvement. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |