-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
haskellPackages.hasura: 2.0.7 -> 2.0.9 #139621
Conversation
@ofborg build hasura-graphql-engine hasura-cli |
Looks like this is at least building on Linux. Thanks! |
@Lassulus Is it intentional that |
hmm, not really. if that is important maybe it can be fixed |
@Lassulus How have you been using hasura-graphql-engine and hasura-cli from nixpkgs by yourself? Have you been using the web console or managing state with hasura-cli? I'm just wondering, if I am still missing something. By default, hasura web console uses UI assets from CDN and that fails, because there is no assets for version hasura-cli, on the other hand, used to use its version to fetch matching plugins, but that was in 1.3.1 and I'm now only learning how 2.x works... Anyway, I try to get these versions to work at first. Thanks for managing to package 2.x for nix! |
not yet, I wanted to but was sadly busy with other stuff. So I haven't come around to actually set it up. You could open up a new issue with you findings and when I come around to actually use it, I can try to fix all the occurring problems. |
@Lassulus Really good to know! I'll try to compose new issues, once I've figure things out. So far, I can confirm, that graphql-engine server itself seems to work as expected, but the web console has broken UI asset CDN url due to invalid hasura-cli will be more complex beast. It is not only a go application, but also contains nodejs-based To summarize, we'll need to more thing to package:
|
Version is passed in via |
@Lassulus FYI. I have now built both console-assets and hasura-cli-ext with nix for myself. If you get far enough to try out Hasura for real before I have polished my work into a pull, just ping me. Building also hasura-cli-ext and wrapping hasura-cli to use it is necessary to support Hasura metadata migrations. And we do want to include console-assets to remove one CDN dependency from the UI. |
@datakurre I'd be interested in your code, even untested. I've been trying out Hasura for a project and while fixing the
|
@zarybnicky https://gist.github.com/datakurre/8ed08e74881b62ae92a393e6e34cebf5 CDN version fix is not necessary if assets are made available and HASURA_GRAPHQL_CONSOLE_ASSETS_DIR set for graphql-engine. Also hasura console command can serve local assets instead of CDN assets. Ugly part in building console assets is that even their own Makefile downloads "common" assets from their CDN. With Nix those should probably be downloaded file by file (the gist simply includes them as tarball). cli-ext is statically linked, because otherwise it would require special surgery similar to
|
@datakurre Thanks! Is this the way Node packages are commonly packaged in Nixpkgs, including the entire node2nix composition in the source tree and using the |
@zarybnicky To be honest, I have not looked, which is the currently preferred way to package Node packages in nixpkgs. I've ended up with way that is flexibly enough for me and have worked in many use cases. |
@Lassulus Would you be able to help or instruct, how to upgrade hasura 2.0.9 to 2.0.10? |
sure, just run |
Motivation for this change
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)