In cloud build, we rely on the source code that we want to build against having been
checkout out to the /workspace directory in the build environment, and the $PWD
of the build environment being that same directory. In short, when the build starts,
your source code repository is checked out in ./, the current directory. From there,
it's easy to refer to different pieces of source code by relative path, and makes using
docker-related tools like docker and docker-compose feel natural, despite the fact
David McGuire dmcguire81
dmcguire81
/ 3-deeper-text-analysis.ipynb
Last active
December 3, 2022 19:57
3-deeper-text-analysis.ipynb
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
dmcguire81
/ main.rs
Last active
March 6, 2019 23:55
Hello world actix-web example with multiple CORS allowed origins
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| extern crate actix_web; | |
| use actix_web::middleware::cors::Cors; | |
| use actix_web::{server, App, HttpRequest}; | |
| fn index(_req: &HttpRequest) -> &'static str { | |
| "Hello world!" | |
| } | |
| fn main() { | |
| server::new(|| { |
dmcguire81
/ README.md
Last active
December 14, 2015 08:49
— forked from mbbx6spp/README.md
This is a mini howto on moving a subdirectory to its own repository retaining history
Assume PARENT is the original parent Git repository (locally) and CHILD is the new local repository that you wish to create from a subdirectory, retaining all of its history from the PARENT repository; PARENT_PATH and CHILD_PATH are the paths to PARENT and CHILD respectively; SUBDIR is the relative path within the repository under extraction:
git clone --no-hardlinks PARENT_PATH CHILD_PATHpushd CHILD_PATH