Skip to content

Commit ac48a13

Browse files
committed
RELEASE 1.0.0 - sesion login with normal view
* the most simple login system, the auth controller just check received params * the index controller(auth) only checks credentials, if sucess then replace to a valid page, otherwise redirect login
1 parent 96efee8 commit ac48a13

File tree

18 files changed

+208
-870
lines changed

18 files changed

+208
-870
lines changed

README.md

Lines changed: 46 additions & 60 deletions
Original file line numberDiff line numberDiff line change
@@ -1,92 +1,78 @@
11
# codeigniter-webapp
22

3-
Template codeigniter repo. just clone or use as started base
3+
Login template for codeigniter repo, this project just use session files, the most simple
44

5-
## Getting started
5+
The project its at https://gitlab.com/codeigniterpower/codeigniter-login
66

7-
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
8-
9-
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
10-
11-
## Add your files
7+
## Installation
128

13-
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
14-
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
9+
Just clone the repo:
1510

1611
```
17-
cd existing_repo
18-
git remote add origin https://gitlab.com/codeigniterpower/codeigniter-webapp.git
19-
git branch -M main
20-
git push -uf origin main
21-
```
22-
23-
## Integrate with your tools
24-
25-
- [ ] [Set up project integrations](https://gitlab.com/codeigniterpower/codeigniter-webapp/-/settings/integrations)
12+
mkdir ~/Devel && ~/Devel
2613
27-
## Collaborate with your team
14+
git clone --recursive https://gitlab.com/codeigniterpower/codeigniter-login
2815
29-
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
30-
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
31-
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
32-
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
33-
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
34-
35-
## Test and Deploy
36-
37-
Use the built-in continuous integration in GitLab.
38-
39-
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
40-
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
41-
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
42-
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
43-
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
44-
45-
***
16+
```
4617

47-
# Editing this README
18+
Then enable "user directory" module into your webserver, change "public_html" to "Devel
19+
and visit `http://localhost/~general/codeigniter-login`
4820

49-
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
21+
## Deploy into your webserver
5022

51-
## Suggestions for a good README
52-
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
23+
Just clone the repo:
5324

54-
## Name
55-
Choose a self-explaining name for your project.
25+
```
26+
mkdir /var/www/html && /var/www/html
5627
57-
## Description
58-
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
28+
git clone --recursive https://gitlab.com/codeigniterpower/codeigniter-login
5929
60-
## Badges
61-
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
30+
```
6231

63-
## Visuals
64-
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
32+
Then enable the site and visit `http://localhost/codeigniter-login`
6533

66-
## Installation
67-
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
34+
## Development
6835

69-
## Usage
70-
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
36+
Its just 4 files:
7137

72-
## Support
73-
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
38+
```
39+
webappweb The Applicaions directory of Codeigniter renamed
40+
|
41+
/controllers Place of the controllers that manages logic
42+
| |
43+
| /Indexauth.php Login controller mechanish to init or end session
44+
| |
45+
| /Indexhome.php Another page entry, will check valid sesion object
46+
|
47+
/views Pages display rendering data from controllers
48+
|
49+
/homesview.php Arbitrary page only viewable under valid session
50+
|
51+
/inicion.php Login view page for init the sesion process
52+
```
7453

75-
## Roadmap
76-
If you have ideas for releases in the future, it is a good idea to list them in the README.
54+
#### Process simple login
7755

78-
## Contributing
79-
State if you are open to contributions and what your requirements are for accepting them.
56+
This is the main entry controller, it will load the views of login form page
57+
to input credentials, also will process such request to validate the login
58+
process of the credentials.
8059

81-
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
60+
```
61+
->user/pass--->Indexauth/index--->Indexauth/auth()---->Indexhome/index (sucess)
62+
|
63+
|---->Indexauth/index (fail)
64+
```
8265

83-
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
66+
The magic is done by the `auth($data = NULL, ... , ... )`
8467

8568
## Authors and acknowledgment
69+
8670
Show your appreciation to those who have contributed to the project.
8771

8872
## License
73+
8974
For open source projects, say how it is licensed.
9075

9176
## Project status
77+
9278
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

index.php

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
/home/general/Devel/codeigniter-login/webappweb.php

webappdb/README.md

Lines changed: 0 additions & 31 deletions
This file was deleted.

webappdb/odbc-README.md

Lines changed: 0 additions & 116 deletions
This file was deleted.

webappfiles/css/index.html

Whitespace-only changes.

webappfiles/files/index.html

Lines changed: 0 additions & 10 deletions
This file was deleted.

webappfiles/index.html

Whitespace-only changes.

webappfiles/js/index.html

Whitespace-only changes.

webappweb/config/config.php

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,10 +23,11 @@
2323
| a PHP script and you can easily do that on your own.
2424
|
2525
*/
26-
$config['base_url'] = (isset($_SERVER['HTTPS']) && $_SERVER['HTTPS'] == 'on') ? 'https' : 'http';
26+
$config['base_url'] = ((isset($_SERVER['HTTPS']) && $_SERVER['HTTPS'] == 'on') || isset($_ENV['FORCE_HTTPS'])) ? 'https' : 'http';
2727
$config['base_url'] .= '://' . $_SERVER['HTTP_HOST'];
2828
$config['base_url'] .= str_replace(basename($_SERVER['SCRIPT_NAME']), '', $_SERVER['SCRIPT_NAME']);
2929

30+
3031
/*
3132
|--------------------------------------------------------------------------
3233
| Index File

webappweb/config/routes.php

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,6 @@
4949
| Examples: my-controller/index -> my_controller/index
5050
| my-controller/my-method -> my_controller/my_method
5151
*/
52-
$route['default_controller'] = 'indexcontroller';
52+
$route['default_controller'] = 'Indexauth';
5353
$route['404_override'] = '';
5454
$route['translate_uri_dashes'] = FALSE;

0 commit comments

Comments
 (0)