digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-11-09 15:37:05 +03:00
Code Issues Projects Releases Wiki Activity
4916a28682
daml/.gitignore

97 lines
1.2 KiB
Plaintext
Raw Normal View History

open-sourcing daml
2019-04-04 11:33:38 +03:00
.DS_Store
._.DS_Store
.stack-work
pkgs/*/.stack-work
workspaces/*/.stack-work
distribution-work
.idea
.envrc.private
*.iml
*.ipr
*.iws
.*.sw?
.sw?
*.pyc
*.o
*.hi
dist/
cache/
target/
target-sbt/
build/
result
.project
.build
/ci-out/
**/codex.tags
/hscope.out
._thesis.pdf
\#*\#
.\#*\#
*.tix
.da-*-gui-state
/pkgs/generated
TAGS
tags
/result-*
**/.settings
**/.classpath
**/.factorypath
*.tgz
web ide: secure docker containers through networks (#304) This pr addresses security concerns regarding the web ide docker container. The bulk of the changes involve managing and coordinating docker networks so that the proxy runs on internal docker network as well as external one, while the web ide containers run only on the internal network.
2019-04-08 22:31:13 +03:00
*.tar.gz
open-sourcing daml
2019-04-04 11:33:38 +03:00
ghc-bindist
*.result.xml
**/.ensime
**/.ensime_cache
ensime.sbt
pipelinePerformance.xml
**/database_test.manifest
.ghci
.ghcid
*.log
.buckd
buck-out
.buckconfig.local
haskell-style-check.txt
da-daml-equities-library.txt
*.egg-info/
.flattened-pom.xml
*~
*.orig
venv
trace.*.dat
node_modules/
/out/
.hpc
hpc-report/
/results
**/latency.csv
**/summary-report.txt
.scannerwork/
**/dump-*.txt
**/*tests.xml
ledger-api/.bin
*.db
.vscode
.m2/
.history/
web ide: secure docker containers through networks (#304) This pr addresses security concerns regarding the web ide docker container. The bulk of the changes involve managing and coordinating docker networks so that the proxy runs on internal docker network as well as external one, while the web ide containers run only on the internal network.
2019-04-08 22:31:13 +03:00
**/.history/
open-sourcing daml
2019-04-04 11:33:38 +03:00
### Bazel: https://www.gitignore.io/api/bazel ###
/bazel-*
Initial boilerplate for cross-version compatibility testing (#5665) This is a first step towards testing cross-version compatibility. It doesn’t actuall do much yet but hopefully it should be easier to parallelize once we have the initial boilerplate in place so ideally I’d like to address most missing things and issues in separate PRs. changelog_begin changelog_end
2020-04-23 13:58:11 +03:00
/compatibility/bazel-*
Make compat tests work on windows (#5732) * Make compat tests work on windows This required some changes to the daml_sdk rule since the read-only installation by the assistant breaks Bazel completely. We could only apply those changes on Windows but I think I prefer the consistency across platforms here over trying to stay close to how the SDK is installed on user machines given that the SDK installation is not something we’ve had issues with. I’ve excluded the postgresql tests for now. I don’t expect them to be particularly hard to fix but I’ve already spent almost 2 days on this and having some tests run on Windows seems like a clear improvement over running no tests on Windows :) changelog_begin changelog_end * Remove todo changelog_begin changelog_end
2020-04-28 17:06:36 +03:00
/compatibility/.bazelrc
open-sourcing daml
2019-04-04 11:33:38 +03:00
.bazelrc.local
.ijwb
.bazelproject
.bazel-cache
Prototype to accelerate Windows development (#411) * Initial rattle prototype * Build the IDE core * Ignore the Rattle directory * Clean up the dependencies * Require stack-1.10, since that does much better extra-dep caching * Streamline the ghc-lib dependencies * Compile more pieces * Add a build.bat * Make the Windows build use the correct stack.yaml to bootstrap * Fix up enough to build on Windows * Generate the dylib's on Mac * Remove accidental -v * Make the Haskell build driven by the Bazel metadata * Get proto3-suite building * Delete the unneeded haskell-dependencies * Allow generating the proto files and compiling them * Fix metadata to deal with """ syntax * Fix metadata to deal with a list of globs * More work in the direction of daml-ghc * Use correct daml_lf proto version * Tell GHC to use shared objects in TH * Specify needed packages * wip * wip * Switch to the fork of gRPC-haskell * Build executables with rattle * setup build.sbt in daml-lf * Build binaries with rattle * rattle-sbt, move scala build scripts out of daml-lf subdir, and into rattle subdir * convert scala-build.sh into MainScala.hs * Clean up rattle build * Pre-merge clean up * Switch to the newer version of ghc-lib-parser * remove dev ls from MainScala.hs * compile java generated from protos as separate projects * Add copyright headers * HLint fixes * Uscrewup an HLint fix * fix scala formatting of rattle/build.sbt
2019-04-12 12:45:11 +03:00
.rattle
daml-lf/project
daml-lf/gen
daml-lf/build.sbt
GroupChat, take 2 (#1671) * GroupChat, take 2 * GroupChat, last member may leave * Add origin field into Group to support the group identity
2019-06-17 12:01:25 +03:00
.markdown-preview.html
dev-env: remove gradle (#2738)
2019-09-04 19:44:51 +03:00
compiler/damlc/output
Hlb update and document external build steps (#2769) * stack setup for HLB and Nim * build_packages.sh and daml-ledger.cabal * update README * export-package for daml-ledger * export-package, run here * find tmp daml-ledger * update README for review comments * ref daml instructions * further improve the process and documentation in response to comments * have -with-rtsopts match the bazel build * fixes for Gary
2019-09-09 16:37:03 +03:00
language-support/hs/bindings/gen
language-support/hs/bindings/*.cabal
language-support/hs/bindings/examples/nim/*.cabal
Add documentation for upgrading using DAML script and triggers (#5465) * Add documentation for upgrading using DAML script and triggers This PR adds documentation for how you can automate the upgrade process from the Coin example using DAML Script and DAML Triggers. Having written this, I think we might want to add some integration tests for this but it’s rather complex to setup since it ties together so many pieces so I’d like to leave it out for now. We do at least test that the code compiles and we all knows that code that compiles never has bugs. changelog_begin changelog_end * Apply suggestions from code review Co-Authored-By: associahedron <231829+associahedron@users.noreply.github.com> Co-authored-by: associahedron <231829+associahedron@users.noreply.github.com>
2020-04-07 15:36:40 +03:00
.daml/
Reference in New Issue Copy Permalink