steid

@jamesgill /

1//! The application layer: use cases and the ports they depend on.
2//!
3//! Every use case takes an actor or a credential plus the ports it needs, and enforces
4//! the rules before any side effect. Nothing here knows about HTTP or Topcoat.
5
6pub(crate) mod authz;
7pub mod browse;
8pub mod claim;
9pub mod config;
10pub mod error;
11pub mod git;
12pub mod identity;
13pub mod login;
14pub mod port;
15pub mod profile;
16pub mod repo;
17pub mod session;
18pub mod token;
19
20pub use browse::{Browsed, FileView, LOG_LIMIT, MAX_BLOB_BYTES, browse_repo, repo_log};
21pub use claim::{OwnerSpec, claim_instance, is_claimed};
22pub use config::AppConfig;
23pub use error::{Error, Result};
24pub use git::{GitClientHeaders, GitEndpoint, GitOperation, GitService, serve_git};
25pub use identity::{Identity, describe_identity};
26pub use login::login;
27pub use profile::{PublicProfile, update_profile, view_profile};
28pub use repo::{NewRepo, RepoSummary, RepoView, create_repo, list_repos, view_repo};
29pub use session::{SESSION_LIFETIME, end_session, record_session, resolve_actor, sweep_expired};
30pub use token::{
31 IssuedToken, TokenSummary, authenticate_token, issue_token, list_tokens, revoke_token,
32};